Guiding feature model evolution by lifting code-level dependencies

Feature models are a de facto standard for representing the commonalities and variability of product lines configurable software systems. Requirements-level features commonly implemented in multiple source code artifacts, resulting complex dependencies at level. As developers add evolve frequently, it is challenging to keep feature consistent with their implementation. This article thus presents an approach combining feature-to-code mappings dependency analyses inform engineers about possible inconsistencies. We focus on code-level changes requiring updates constraints. Our uses static analysis variation control system lift models. present suggested engineer two ways: directly as links between model heatmap visualizing all model. evaluate our by analyzing evolution history case study systems: Pick-and-Place Unit KePlast line industry partner KEBA AG. results evaluating utility (RQ1) performance (RQ2) approach, well quality suggestions (RQ3).